home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group93c.txt
/
000086_icon-group-sender _Fri Nov 12 21:30:33 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1994-02-02
|
1KB
Received: by cheltenham.cs.arizona.edu; Sat, 13 Nov 1993 16:50:04 MST
Date: Fri, 12 Nov 93 21:30:33 CST
From: jeffery@runner.jpl.utsa.edu (Clinton L. Jeffery)
Message-Id: <9311130330.AA14375@runner.utsa.edu>
To: icon-group@cs.arizona.edu
In-Reply-To: <1993Nov3.105756.909@sics.se> (pipex!uknet!mcsun!sunic!sics.se!sics.se!soder@uunet.uu.net)
Subject: Re: Icon debugging and MT-Icon
Content-Length: 830
Status: R
Errors-To: icon-group-errors@cs.arizona.edu
> Hakan Soderstrom writes:
> Knowing next to nothing about MT-Icon, my question is: Will MT-Icon
> obviate the need for other debugging extensions to Icon?
Yes, MT Icon is intended to allow the construction of debuggers for Icon
in Icon. An Icon program can load another Icon program (producing a
co-expression value corresponding to a call to its main() procedure),
and then control its execution, inspect and modify its variables, etc.
Execution control is driven by an event model.
We have mostly used it so far for program visualization tools, and there
are one or two things (like variable traps) I'd like to add especially
for debugging, but the code for MT Icon and monitoring has been used for
some time now by a number of people.
Clint Jeffery, jeffery@ringer.cs.utsa.edu
The University of Texas at San Antonio